TrustRadius Insights
Docker has proven to be a versatile tool with a wide range of use cases. Users have found that Docker simplifies the packaging and …
Starting at $500 per year per node
View PricingOverview
What is Mirantis Kubernetes Engine?
The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters…
Recent Reviews
Pricing
Free
$0.00
Cloud
per year
Basic
$500.00
Cloud
per year
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://store.mirantis.com
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $500 per year per node
Product Details
- About
- Tech Details
- FAQs
What is Mirantis Kubernetes Engine?
Mirantis Kubernetes Engine Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Frequently Asked Questions
The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters on any infrastructure: public cloud, private cloud, or bare metal.
Mirantis Kubernetes Engine starts at $500.
Reviewers rate Support Rating highest, with a score of 7.8.
The most common users of Mirantis Kubernetes Engine are from Mid-sized Companies (51-1,000 employees).
Comparisons
Compare with
Reviews and Ratings
(210)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Recommendations
Docker has proven to be a versatile tool with a wide range of use cases. Users have found that Docker simplifies the packaging and deployment of applications and services, allowing developers to match their development environment to production and eliminate cross-cutting software dependencies. It has been utilized as the backbone of a hosted app infrastructure, where every element is broken down into microservices deployed on the AWS cloud. Additionally, Docker has been instrumental in creating specialized microservices such as a Selenium Grid for automated web-based testing.
Moreover, Docker has played a crucial role in maintaining environmental consistency and streamlining deployment processes. It has enabled users to swiftly containerize Continuous Deployment and Integration pipelines, facilitating easy deployment and updates of the system and its environments. With Docker, users have been able to quickly deploy and monitor servers, firewalls, switches, and other components, providing a consistent and efficient environment for prototyping and testing. Another notable use case is spinning up new databases for microservices using Docker, ensuring consistency and independence across different environments.
Furthermore, Docker has integrated seamlessly with orchestration frameworks like Apache Mesos and Mesosphere Marathon. This combination has allowed for more efficient application development and deployment through effective management of containers. Docker has also demonstrated its utility in building server deployment files and running tests, enabling consistent deployments and reliable testing procedures.
In addition to these technical applications, Docker has proved to be valuable in hosting MySQL databases for production websites. Its stability, security features, and easy provisioning of identical instances have made it a preferred choice for users. Moreover, Docker has been extensively used in CI builds as it enables the creation of custom Linux images and seamless deployment of the latest code from the Docker registry.
The flexibility offered by Docker comes to the forefront when it comes to testing practices. It provides a highly configurable environment that makes cross-platform testing significantly more efficient. Users have leveraged Docker for both automated website/application testing pipelines as well as creating flexible environments for manual testing. Moreover, Docker has acted as a viable alternative to custom build and deploy solutions, offering a more flexible and decentralized process.
Notably, Docker has been embraced by a large global financial services provider to enhance efficiency and agility in application development. This adoption has resulted in increased innovation and productivity within the organization. Another significant benefit of using Docker is its ability to provide identical application environments across multiple deployment environments, leading to the deployment of more stable applications.
Furthermore, Docker has played a role in differentiating between server/compute infrastructure and application infrastructure. Operations teams can efficiently manage the cluster of servers, while application developers can run containers on the cluster, ensuring a clear separation and easier management of the two layers.
Teams have leveraged Docker for various development and deployment practices. Engineers can build applications in the same environment, eliminating local configuration issues that often arise when working across different setups. Docker has been particularly useful for WordPress development, replacing tools like Vagrant and providing tighter integration with Windows Hyper-V and better performance.
One of the significant advantages of Docker is its ability to containerize applications, resulting in consistent deployment environments across different stages and compatibility with various cloud platforms. This has greatly simplified the deployment process for users and enhanced their productivity. Additionally, Docker has been highly beneficial for the development team in resolving issues related to different setups on Windows, Linux, and Mac operating systems, while also providing easy configurations for automation QA.
Docker's impact extends beyond software development into the realm of research reproducibility. Users have developed Docker containers to encapsulate research pipelines, leveraging GitHub and DockerHub as public repositories. This approach has effectively addressed the challenge of ensuring reproducibility in research experiments.
Moreover, Docker Swarm has been employed to deploy internal applications in a managed cluster, successfully tackling scaling and load balancing issues during peak business hours. The combination of Docker with Kubernetes has also gained popularity among teams for containerizing projects and facilitating the development of microservices.
Overall, Docker's value proposition lies in its ability to provide consistent development environments, prevent deployment issues, streamline configurations, enhance testing efficiency, and simplify the overall software packaging and deployment processes. Its widespread usage across various industries highlights its robustness, ease of setup, community support through open-sourced images, and its ability to create and test configurations as needed. Docker has become an indispensable tool for many organizations seeking to optimize their software development lifecycle while improving productivity and innovation.
Based on the reviews, here are the three most common recommendations:
-
Users recommend trying Docker for deploying web services and running micro-services. They suggest doing tutorials to learn how to create Dockerfiles and docker-compose files correctly. Additionally, they advise considering whether Docker is necessary or if statically linked binaries can be used instead.
-
Users also recommend using Docker for QA environments and setting up developers with the environment they need. They find Docker to be an easy-to-use development tool with great rewards for a small amount of effort. However, some users caution that while Docker is a good solution, there may be better alternatives available.
-
Another common recommendation is to carefully consider the use of Docker in a workflow and discuss its usability within the organization before implementing it. Users emphasize the importance of learning the basics of Docker and understanding if continuous integration/deployment is the right approach. They also mention that Docker has a supportive community and is widely used in the industry.
Overall, users suggest experimenting with Docker, especially for new applications or running micro-services. They recommend taking advantage of Docker's simplicity and portability while being mindful of specific requirements and considering other options if needed.
Attribute Ratings
Reviews
(1-22 of 22)Companies can't remove reviews or game the system. Here's why
June 25, 2021
With Docker consider it done
Docker Enterprise is quite a handy solution when it comes to containerizing your application making it lightweight and easy to spin and access. Currently, it is being used across the whole organization and [is a] solution for every kind of complex problem.
- Easy to control.
- Setting up network across different containers is quite easy.
- Mapping of resources with host machine is easy.
- Setting up networking from scratch is painful.
- Resources required for setting Docker Enterprise are huge.
- User interface needs to be improved and made more user friendly.
Through
[Mirantis Cloud Native Suite (Docker Enterprise)] I have got rid of the improperly-signed and even unsigned container
workloads. This tool is easy to configure and easily I can tag the workloads
for execution on appropriate node types. Further through this application, it is
very convenient for me to use specialized hardware in bare metal which includes
FPGAs and GPUs, that offer great machine learning and helps in scientific
computing.
- It is advanced tool for balancing loads and managing routes.
- It is easy to edit container contents.
- Alerts are very useful which helps us handling the entire network.
- I am mostly satisfied with all of its features but I have faced issues in the continuous data storage no doubt they offer features like Dockers Data Volumes but still there is much room for improvement.
- Moreover, I am a happy user of this platform.
December 19, 2019
Docker: If you don't bring up and take down a few tens of dockers a day, then you really need to start doing so
Docker is everywhere, there just isn't a server on an application which is not present in Docker. It forms the integral part of the whole infra for us. The beauty of Docker comes from its amazing quality of being robust, easy to start and very easy to blow it off completely. It's the most powerful tool which just does magic for us.
- Robust.
- Easy to setup.
- The kernel cannot be changed.
August 14, 2019
Productivity Booster
Docker is used by most of our teams as part of their development and deployment practice. For development, it enables engineers to build applications in the same environment without worrying about local configuration issues. Nearly all of our CI/CD and infrastructure runs in Docker containers as well, which makes debugging production issues (especially around deployment) as simple as pulling down the right image and poking at it locally.
- Isolation of dependencies.
- "Black box" services like databases and packaged applications.
- Infrastructure as code.
- The CLI can take some getting used to if you aren't familiar with it.
- For running many Docker containers locally, you'll need a lot of disk and RAM.
- There are a lot of concepts to be familiar with when learning Docker, and the documentation could be more beginner-focused.
We use Docker for WordPress development. It has replaced Vagrant on our development systems. We like the tighter integration with Windows Hyper-V and the performance is better than VirtualBox-based solutions. We are able to jump-start many projects with the Docker Compose files people contribute and publish on GitHub. Using Docker Compose we are able to create reliable, consistent, development scaffolding.
- High performance.
- Easy to configure consistent development systems.
- Eliminates the "It works on my machine" problem.
- Tighter integration with Windows 10 and WSL.
- Better support for MacOS.
- Better documentation.
August 27, 2018
Very useful for testing purposes
We use Docker mainly for testing purposes. To avoid issues with local environments while testing our site, we use Docker images. This has many benefits: you can easily add/remove configurations and extras. For example on PHP you can try different images with different versions of PHP. Trying to achieve this on your localhost (for example with XAMPP or something more friendly) is very time-consuming.
I should say I know Docker is meant for something more pro and I'm a light user; I don't push a Docker image completely to a server, but for testing purposes it has been extremely useful. You can use CLI for changing things, you can create different databases, alter them and load them again, etc.
I should say I know Docker is meant for something more pro and I'm a light user; I don't push a Docker image completely to a server, but for testing purposes it has been extremely useful. You can use CLI for changing things, you can create different databases, alter them and load them again, etc.
- Creating and deleting "server" images is way easier than normal. You can change configurations and it basically creates a virtual machine on your computer, but WAY easier than using VMWare yourself. It's a layer on top of that.
- Getting images is pretty easy, there are many on the internet and you can get help from the community in some cases you are not sure what to do
- The commands in Docker work pretty well. There is good documentation and you can achieve almost anything considering a virtual machine.
- Maintaining stability between environments thanks to the Docker app. You can have the SAME exact app on different systems (MacOS vs Win) and it will behave 99% the same.
- As a NON-heavy user, definitely it's a bit intimidating in the onboarding phase. It's hard to understand what everything is for and how to use it appropriately. As I wrote before, this could be because I'm not a hard developer myself.
- At least on Windows 10, I always have problems turning it on. It has problems starting, I need to quit/start again, and then it works. I'm supposed to have a stable version, not sure if it's only myself.
August 01, 2018
Docker is containers within containers
Docker is truly an amazing tool that is used across our organization. It gives the developer tools to easily set up environments, deploy code, CI pipeline. Open sourced images and community supports makes it a great choice.
- Setting up Docker containers helps developers to replicate the production environment frim their local machine in a virtual box. This helps keep development and debugging simple.
- Portability is really helpful. You can easily shift from AWS to GCP within minutes.
- Docker images are version-controlled just like github commits.
- User friendly - creating the virtual environment takes a lot more time than running the shell script to set up the environment.
- Docker containers are for running applications and not for data containers. Having that feature would be awesome.
- Docker image and containers prune command to force-delete all the images and containers as a cleanup.
Docker is being used across our organization for product development and deployment. We switched to docker in order to replace a custom build and deploy the solution. We have used it as part of our build and deploy system to make the process more flexible and decentralized. It has made it much easier to build out new data centers and is part of our internationalization strategy.
- Docker provides encapsulation of our deployed software. This allows us to consistently deploy each of our services and webs in a customizable manner.
- Docker makes it easy to build and release software in both development and production environments
- Docker allows us to build common baseline environments for consistency across apps while adding app-specific customizations.
- We have had problems using Docker for local development. There are issues with how it works with our asset build system.
June 19, 2018
Docker for Quick and Easy Container Deployments
Docker is being used as a quick way for organizations to deploy Couchbase as a container, both independently and in an orchestrated environment. Because of how easy Docker containers are to create and destroy, it makes developer and operations work incredibly easy for prototyping in a consistent environment using the Docker runtime.
- Container environment consistency
- Lightweight deployments
- Cross-platform
- Hyper-V can cause problems for configuration on Windows environments
March 23, 2018
Hive Mind Your Frontend
We are using Swarm for our analytics gathering service. Using swarm allows for quick workload scaling and using less hardware than was needed before.
- Creating complex containers using docker files which automate a lot of DevOps manual labor
- Having some preconfigured containers to do fast tests
- The swarm takes away a lot of the work you would need to do for high availability
- Kitematic UI is still very limited in functionality
- Containers on Windows are somewhat hit and miss, Linux is strongly recommended
- Swarm interface is mostly command line
- Some network limitations (like remote client IP passthrough)
August 16, 2017
Docker FTW!
We use Docker to containerize our applications, we get many benefits from this such as:
- consistent, realizable deployment environments across dev, QA, prod - the same image used in dev is the exact same image deployed to production
- better utilization of server resources
- cross cloud compatibility
- the ease of scaling applications
- Docker makes deployments easier across environments.
- Docker allows to better utilization of server resources by easily allowing multiple applications (images) to run on the same server.
- Docker makes it easy to scale our applications out.
- Docker is somewhat new and new functionality comes with each release, sometimes it can be hard to stay on top of all the new features.
- It would be nice if a full GUI based container management system came with Docker.
August 15, 2017
Docker for QA: dockerized Selenium Grid
Docker is used for by both the dev team and the QA team on my project. For the dev team it's really useful as they had a lot of issues prior to using Docker with the different setups the devs had: Win/Linux/Mac. After switching to Docker these issues disappeared.
For me as an automation QA lead, it's mainly used for our Selenium Grid. Our grid is running on AWS, and I configured it via Docker. I use docker-compose to start it up and to scale how many browsers should be started. Using only Docker was already a huge help, as we didn't really have to worry about the configurations and it was easy to use the same setup for more instances, but combined with the scaling option of docker-compose it proved to be a really convenient.
For me as an automation QA lead, it's mainly used for our Selenium Grid. Our grid is running on AWS, and I configured it via Docker. I use docker-compose to start it up and to scale how many browsers should be started. Using only Docker was already a huge help, as we didn't really have to worry about the configurations and it was easy to use the same setup for more instances, but combined with the scaling option of docker-compose it proved to be a really convenient.
- Develop on multiple platforms. The same Docker image can be used on Linux/Mac/Windows.
- Ease of configuration. It's very easy to create a base image for your project. There are a lot of already existing images you can use to start with.
- Scalability. If you need more than just one instance of the same image, it's just a command to spin up more.
- Finding the perfect configuration: it's very easy to find some basic configurations, but fine-tuning it can be challenging.
- Understanding the concept can be difficult at first. Most of the question I get from colleagues are around: what's happening inside the docker, how we can see the logs what happens inside etc. One you have the concepts, you can easily do these, but this can be a rough beginning.
- Sometimes difficult to set it up. I'm mainly hearing about this from colleagues using Windows.
August 04, 2017
Docker, Pros, Cons, Use Cases
A large global financial services provider based in London, faced increasing regulatory pressure and market demands—led by industry disruptors offering modern, digital services. Looking to increase innovation and productivity, Barclays set out to build an Application Platform-as-a-Service as part of its cloud program. It used Red Hat OpenShift Container Platform which incorporates Docker, along with other Red Hat solutions to update its IT infrastructure and adopt an agile, DevOps approach to application development, giving its developers on-demand, self-service capabilities. As a result, the bank improved its efficiency and agility to innovate faster and stay competitive.
- Docker brings in an API for container management, an image format and a possibility to use a remote registry for sharing containers. This scheme benefits both developers and system administrators.
- Docker allows for portability across machines. The application and all its dependencies can be bundled into a single container that is independent of the host version of Linux kernel, platform distribution, or deployment model. This container can be transfered to another machine that runs Docker and executed there without compatibility issues.
- Docker has a lightweight footprint and minimal overhead. Docker images are typically very small, which facilitates rapid delivery and reduces the time to deploy new application containers.
- Docker allows for sharing. You can use a remote repository to share your container with others.
- Docker provides great version control and component reuse. You can track successive versions of a container, inspect differences, or roll-back to previous versions. Containers reuse components from the preceding layers, which makes them noticeably lightweight.
- Docker has got into the bad habit of wrapping open source Linux technologies and promoting them in a way that makes it feel like Docker invented it. They did it to LXC and they are doing it to aufs and overlayfs.
- Docker is not very developer friendly.
- Docker containers are currently for software, not for data.
- New Docker versions cause breakage. You need all kinds of subtle regressions between Docker versions. It’s constantly breaking unpredictable stuff in unexpected ways.
- Docker does not have a command to clean older images, lifecycle management.
- Lack of kernel support.
We use Docker as the backbone of our hosted app infrastructure. Every element of our application is broken down into a microservice; these miniature services are then built into Docker containers and deployed directly to AWS cloud. Docker lets us deterministically build, distribute, and deploy all of our services without any ambiguity as to what's being deployed and why.
- Deterministic application state and deployments.
- Consistent version history for previous builds.
- Easy distribution mechanisms across the team.
- Docker does update quickly, sometimes the updates to the engine break older container images.
- Some of the changes to the Dockerfile structure are confusing and incompatible with older versions, challenging teams.
April 03, 2017
Docker is for microservices and app delivery
We are using Docker today to spread multiple Tomcat instances across a single machine. Docker is currently being used by our devops team but we're a small company so that's pretty much the entire infrastructure team as well. Docker helps us keep our configs simple, easy to use, and reproducible in a really efficient manner.
- Docker makes it very easy to reproduce a service build and configuration. This is huge for rolling out quickly and efficiently.
- Docker can orchestrate your containers to auto scale up and down with Docker Compose. This is very useful on cloud providers where you pay for instance to keep prices down.
- Docker's intra-container networking works well for the most part but it does leave something to be desired when attempting to weave a complex deployment of microservices across multiple bare metal machines and networks. It would be nice to introduce some sort of modeling tool into container networking.
- A really neat feature for Docker could be to have an option to analyze container utilization and alert or notify on suggestions to improve efficiency.
March 24, 2017
Docker rocks!
We are just beginning to use Docker for some specialized microservices within our existing server infrastructure. Specifically, we use it to run a Selenium Grid for automated web-based testing. We are considering broader adoption of Docker within areas such as Java application deployment, local development environments, and continuous integration. Docker primarily helps us maintain environmental consistency (having the same environment from local development to deployment in the cloud).
- abstracting the virtualization aspects so that I don't need to know every detail (even to the point of not needing to know if Docker is using a VM behind the scenes or not)
- providing a simple yet powerful configuration scheme
- huge selection of base containers and easy way to derive from them
- automated builds through Docker Hub
- multiple configuration file versions can be a little confusing
- experienced some downtime with Docker Hub, though it was cleared up quickly
- not really a con of Docker, but it takes some time to learn the concepts of containers and adapt to that way of thinking. Perhaps it would be helpful to have a "Docker for Old School Sys Admins" guide that helps explain some of the differences in concepts and execution when working with containers.
February 27, 2017
Docker killed the sysadmin, but it did not kill the developer
Docker is being used primarily to host a MySQL database that runs a production website. It has been very stable and easy to work with, and we like the security that containerization affords.
- Security by isolation.
- Ease of deployment.
- Flexible configuration.
- Scalability.
- Resource management.
- Administration simplicity.
February 20, 2017
Docker for development is really amazing
We're using Docker with Apache Mesos and Mesosphere Marathon for orchestration. Many departments are using it to develop and deploy applications.
- Docker is really good to develop applications in an isolated environment
- Compose different services to make your application infrastructure
- Docker uses a daemon. This is a single point of failure for an infrastructure that provides many containers. If you need to restart this daemon, you will lose all your containers.
February 15, 2017
Simple Up and Running Script Based Containerization
We use Docker to provide us fast containerization of our Continuous Deployment and Integration pipelines. Once our code is good for shipping, we trigger a test pipeline which will in turn compile all its dockerfiles, upload them to hub.docker.com if needed and then upload/install an updated version of the system and its environments at DigitalOcean via Docker drivers and swarm. Our developers as well as our production servers use it as well, being our stack composed of a total of 4 different nodes, a MongoDB container; an elasticsearch container; a nodejs container and our discovery service container, comprising Consul key-value database to store all data from our slave nodes. It's solely maintained by our development team, but the system built within is widely used by our staff as well as the company's clients, spread throughout the world.
- Its topology isolation is in my opinion an unbeatable feature. In our systems we have the need of parallel Java 7 and 8 versions to be running together. Without Docker that would not have been made possible.
- Docker Swarm, taking care of our load-balance characteristics so needed for our systems is a must have.
- Docker composer is a very powerful feature, therein I can have my containers scripted and each of its continuous integration and deployment separated with each of its own concerns isolated whilst all being nicely bootstrapped together under the same "docker-compose up" command.
- Some commands are not very intuitive. In order to have an entire swarm properly functioning [specifically for the scenario we have at our company] wasn't a simple task, having to maintain a very wide range of environment variables safely and nicely kept and good for use. The pipeline to have such a topology ready wasn't simple to figure out how to come up with.
- Some volumes, if not properly shut down when its necessary, will take up to all your disk space. The extra -v attribute wasn't too obvious to use when removing an specific volume leading us to a huge headache.
- Some containers, though exposed as official ones at docker.hub.com, are very space and memory consuming. We have do figure out our own containers for pretty much everything, even though the services that were necessary in the containers were pretty vanilla.
March 14, 2016
Docker Rocker
We use docker in our CI builds from creating a custom Linux image to deploying our latest code from docker registry
- Simplicity/ Efficiency
- Isolation/ Separation of Concerns
- Works well with cloud deployments using services like AWS
- Supports build automation with docker registry
- I understand docker is evolving very well, however wish there were more logging support
- A Docker dashboard that gives insights and statistics
March 11, 2016
Docker...a huge win!
We are using Docker to deploy multiple services for our company.
Docker allows us to deploy more stable apps, since containers provide an identical application-environment across multiple deployment-environments.
Docker also allows us to differentiate between server/compute infrastructure and application infrastructure.
Ops manages the cluster of servers, while application developers simply run containers on the cluster.
Docker allows us to deploy more stable apps, since containers provide an identical application-environment across multiple deployment-environments.
Docker also allows us to differentiate between server/compute infrastructure and application infrastructure.
Ops manages the cluster of servers, while application developers simply run containers on the cluster.
- Application Runtime Provisioning: Instead of requiring a devops engineer to craft a lengthy provisioning configuration for an application, Devs can easily create a Dockerfile that builds the exact runtime needed for their applications
- Polygot environments: Now that services are are individually provisioned for their task (as opposed to servers provisioned for their task) polyglot services are much more simple. Using the best-tool-for-the-job is simple
- Scaling is easy: Need to scale a service from 5 to 15 nodes? Simply run 10 more containers across the server cluster. Startup is near instant for containers.
- Application Architecture has Improved: Before Docker, our team was nowhere close to 12-factor applications. Docker has allowed us to still manage our own infrastructure, yet we're now building highly-scalable 12-factor apps.
- Service registration and discovery could easily be implemented into Docker/Swarm and would make new-infrastructure startup much simpler.
March 09, 2016
Docker for research reproducibility
As a research organization, we utilize and develop bioinformatics tools as our contribution to the research communities. In particular, we address the research reproducibility issues by developing Docker containers to wrap our research pipelines. Currently we use GitHub and DockerHub as a public repository for other users. Since the users are targeted for a wide range of users (not necessarily tech savvy), graphical user interface is essential. One of the challenges that Docker users currently face is to deliver the graphical user interface from Docker to the user.
- Light weight and portable.
- Easy to share (either by Docker file or as a container/DockerHub).
- Same environment regardless of users operating system.
- Docker is mainly a command line tool; delivering a graphical users interface out of a container is still a problem.
- When Docker runs within a VM as in the case of Mac and Windows users, transferring files in and out of Docker is challenging.
- Since with Mac and Windows users Docker runs within a VM, there's an extensive overhead that need careful consideration.